Configuration of transmission order of uplink data

ABSTRACT

A method for configuring transmission order of uplink data, performed by an REC of an access node. The REC has an interface to an RE of the access node. The method comprises providing instructions to the RE how to prioritize transmission order of uplink data. The uplink data is received by the RE on a radio interface and is to be transmitted from the RE to the REC on the interface. The REC thereby configures the transmission order.

PRIORITY

This application is a continuation of U.S. application Ser. No.15/523,794, filed May 2, 2017, which is a 371 of InternationalApplication No. PCT/SE2017/050217, filed Mar. 8, 2017, and claimspriority to International Application No. PCT/SE2016/051035 filed Oct.25, 2016, the disclosures of which are fully incorporated herein byreference.

TECHNICAL FIELD

Embodiments presented herein relate to a method, a radio equipmentcontroller, a computer program, and a computer program product forconfiguring transmission order of uplink data. Embodiments presentedherein further relate to a method, a radio equipment, a computerprogram, and a computer program product for prioritized transmission ofuplink data.

BACKGROUND

In communications systems, there may be a challenge to obtain goodperformance and capacity for a given communications protocol, itsparameters and the physical environment in which the communicationssystem is deployed.

For example, the introduction of digital beamforming antenna systems inaccess nodes, such as radio base stations, etc., could allow multiplesimultaneous narrow beams to be used to provide network access to, andthus serve, multiple simultaneous terminal devices, such as userequipment (UE), etc. However, the current split in the access nodesbetween a radio equipment controller (REC) and a radio equipment (RE) asinterconnected by the Common Public Radio Interface (CPRI) may no longerbe feasible as passing the data for each individual radio chain over theCPRI interface could drive prohibitively high data rates.

In more detail, the bit rate of the current CPRI interface scalesdirectly to the number of independent radio chains in the RE. Whenhaving e.g., a 200 MHz carrier bandwidth and 128 physical antennaelements in the beamforming antenna system, a bit rate of 530 Gbps wouldbe needed for the CPRI interface with currently used sample rate andsample bit width. A further potential drawback with CPRI is the extralatency from uplink (UL; from terminal device to access node) samplingto the time the data can be used in downlink (DL; from access node toterminal device), as any information based on sampled data needs to belooped back from REC if to be used in RE.

One way to address the above-mentioned issues is to collapse the CPRIbased architecture by removing the CPRI interface and putting thefunctionality of the REC in the RE. This approach has at least twodrawbacks. Firstly, due to faster technological development of the RECcompared to the RE, the technical lifetime of the REC is assumed to beshorter than that of the RE. Replacing the RE is more costly thanreplacing the REC. From this aspect it could thus be beneficial to keepthe functionality of the RE as simple as possible. Secondly, the RECcould be configured to make decisions spanning over multiple REs inorder to make coordinated multi-sector decisions, e.g. when some REsrepresent coverage regions of the access node within the coverageregions of other REs (e.g. a so-called micro cell within a so-calledmacro cell). A collapsed architecture loses this overarchingcoordination possibility.

Hence, there is a need for an improved communication between the REC andthe RE.

SUMMARY

An object of embodiments herein is to enable efficient communicationbetween the REC and the RE.

According to a first aspect there is presented a method for configuringtransmission order of uplink data. The method is performed by an REC ofan access node. The REC has an interface to an RE of the access node.The method comprises providing instructions to the RE how to prioritizetransmission order of uplink data. The uplink data is received by the REon a radio interface and is to be transmitted from the RE to the REC onthe interface. The REC thereby configures the transmission order.

According to a second aspect there is presented an REC of an access nodefor configuring transmission order of uplink data. The REC has aninterface to an RE of the access node and comprises processingcircuitry. The processing circuitry is configured to cause the REC toprovide instructions to the RE how to prioritize transmission order ofuplink data. The uplink data is received by the RE on a radio interfaceand is to be transmitted from the RE to the REC on the interface. TheREC thereby configures the transmission order.

According to a third aspect there is presented an REC of an access nodefor configuring transmission order of uplink data. The REC has aninterface to an RE of the access node. The REC comprises processingcircuitry and a storage medium. The storage medium stores instructionsthat, when executed by the processing circuitry, cause the REC toprovide instructions to the RE how to prioritize transmission order ofuplink data. The uplink data is received by the RE on a radio interfaceand is to be transmitted from the RE to the REC on the interface. TheREC thereby configures the transmission order.

According to a fourth aspect there is presented an REC of an access nodefor configuring transmission order of uplink data. The REC has aninterface to an RE of the access node. The REC comprises a providemodule configured to provide instructions to the RE how to prioritizetransmission order of uplink data. The uplink data is received by the REon a radio interface and is to be transmitted from the RE to the REC onthe interface. The REC thereby configures the transmission order.

According to a fifth aspect there is presented a computer program forconfiguring transmission order of uplink data. The computer programcomprises computer program code which, when run on processing circuitryof an REC of an access node having an interface to an RE of the accessnode, causes the REC to perform a method according to the first aspect.

According to a sixth aspect there is presented a method for prioritizedtransmission of uplink data. The method is performed by an RE of anaccess node. The RE has an interface to an REC of the access node. Themethod comprises receiving instructions from the REC how to prioritizetransmission order of uplink data. The uplink data is received by the REon a radio interface and is to be transmitted from the RE to the REC onthe interface. The method comprises transmitting the uplink data on theinterface according to the instructions, resulting in prioritizedtransmission of the uplink data.

According to a seventh aspect there is presented an RE of an access nodefor prioritized transmission of uplink data. The RE has an interface toan REC of the access node and comprises processing circuitry. Theprocessing circuitry is configured to cause the RE to receiveinstructions from the REC how to prioritize transmission order of uplinkdata. The uplink data is received by the RE on a radio interface and isto be transmitted from the RE to the REC on the interface. Theprocessing circuitry is configured to cause the RE to transmit theuplink data on the interface according to the instructions, resulting inprioritized transmission of the uplink data.

According to an eighth aspect there is presented an RE of an access nodefor prioritized transmission of uplink data. The RE has an interface toan REC of the access node. The RE comprises processing circuitry and astorage medium. The storage medium stores instructions that, whenexecuted by the processing circuitry, cause the RE to performoperations, or steps. The operations, or steps, cause the RE to receiveinstructions from the REC how to prioritize transmission order of uplinkdata. The uplink data is received by the RE on a radio interface and isto be transmitted from the RE to the REC on the interface. Theoperations, or steps, cause the RE to transmit the uplink data on theinterface according to the instructions, resulting in prioritizedtransmission of the uplink data.

According to a ninth aspect there is presented an RE of an access nodefor prioritized transmission of uplink data. The RE has an interface toan REC of the access node. The RE comprises a receive module configuredto receive instructions from the REC how to prioritize transmissionorder of uplink data. The uplink data is received by the RE on a radiointerface and is to be transmitted from the RE to the REC on theinterface. The RE comprises a transmit module configured to transmit theuplink data on the interface according to the instructions, resulting inprioritized transmission of the uplink data.

According to a tenth aspect there is presented a computer program forprioritized transmission of uplink data, the computer program comprisingcomputer program code which, when run on processing circuitry of an REof an access node having an interface to an REC of the access node,causes the RE to perform a method according to the sixth aspect.

According to an eleventh aspect there is presented a computer programproduct comprising a computer program according to at least one of thefifth aspect and the tenth aspect and a computer readable storage mediumon which the computer program is stored. The computer readable storagemedium could be a non-transitory computer readable storage medium.

Advantageously these methods, these RECs, these REs, and these computerprograms allows for efficient communication between the REC and the RE.

Advantageously these methods, these RECs, these REs, and these computerprograms enable the REC to configure the RE (and the RE to be configuredby the REC) as needed. The RE does therefore not need to bepre-configured to use a certain prioritization mode. That is, the RECinstructs the RE not only to prioritize the transmission order of theuplink data as such, but the REC instructs the RE how the prioritizationis to be performed, thereby enabling flexible configuration of the RE.

It is to be noted that any feature of the first, second, third, fourth,fifth, sixth seventh, eight, ninth, tenth and eleventh aspects may beapplied to any other aspect, wherever appropriate. Likewise, anyadvantage of the first aspect may equally apply to the second, third,fourth, fifth, sixth, seventh, eight, ninth, tenth, and/or eleventhaspect, respectively, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing detailed disclosure, from the attached dependent claims aswell as from the drawings.

Generally, all terms used in the claims are to be interpreted accordingto their ordinary meaning in the technical field, unless explicitlydefined otherwise herein. All references to “a/an/the element,apparatus, component, means, module, step, etc.” are to be interpretedopenly as referring to at least one instance of the element, apparatus,component, means, module, step, etc., unless explicitly statedotherwise. The steps of any method disclosed herein do not have to beperformed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

The inventive concept is now described, by way of example, withreference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating an access node according toembodiments;

FIGS. 2, 3, 4, and 5 are flowcharts of methods according to embodiments;

FIG. 6 is a schematic illustration of downlink traffic bit rate as afunction of time according to embodiments;

FIG. 7 is a schematic illustration of allocation of resources in atime/frequency grid according to embodiments;

FIG. 8 is a schematic illustration of prioritized transmission order ofuplink data according to embodiments;

FIG. 9 is a schematic diagram showing functional units of a radioequipment controller according to an embodiment;

FIG. 10 is a schematic diagram showing functional modules of a radioequipment controller according to an embodiment;

FIG. 11 is a schematic diagram showing functional units of a radioequipment according to an embodiment;

FIG. 12 is a schematic diagram showing functional modules of a radioequipment according to an embodiment; and

FIG. 13 shows one example of a computer program product comprisingcomputer readable means according to an embodiment.

DETAILED DESCRIPTION

The inventive concept will now be described more fully hereinafter withreference to the accompanying drawings, in which certain embodiments ofthe inventive concept are shown. This inventive concept may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided by way of example so that this disclosure will be thorough andcomplete, and will fully convey the scope of the inventive concept tothose skilled in the art. Like numbers refer to like elements throughoutthe description. Any step or feature illustrated by dashed lines shouldbe regarded as optional.

FIG. 1 is a schematic diagram illustrating an access node 100 whereembodiments presented herein can be applied. The access node could be aradio base station such as a radio access network node, base transceiverstation, node B, evolved node B, or access point. As disclosed above,the access node comprises at least one Radio Equipment Controller (REC)200 a, 200 b and at least one Radio Equipment (RE) 300 a, 300 b. In theillustrative example of FIG. 1 the access node comprises two RECs andtwo REs, where each REC has an interface 700 to the REs; the interface700 will hereinafter be denoted an REC-RE interface 700. Preferably, theREC-RE interface 700 is a wired interface, e.g. using optical fibercommunications. However, alternatively the REC-RE interface 700 is awireless interface, e.g. using radio communications. Further propertiesof the REC-RE interface 700 between the REC and the RE will be disclosedbelow. The REs are configured to perform DL transmissions to, and ULreceptions from, terminal devices 600 in beams 500 by using appropriatebeamforming weights at the antennas of the radio interface 400 at theRE. The beamforming weights define at least the pointing direction andthe width of the beams.

The REC-RE interface 700 between REC 200 a, 200 b and RE 300 a, 300 bcould be a packet-based interface, and hence not a streaming interface.This allows for quick and flexible allocation of resources on the REC-REinterface 700 to different terminal devices 600. The REC is configuredto maintain knowledge about the terminal devices, and schedules the airinterface between the access node and the terminal devices. The RE isconfigured to act on commands received from the REC.

As an illustrative example, consider a communications system having anair interface with a system bandwidth of 400 MHz and that providessupport for 4 MIMO streams and utilizes access nodes with 64 antennasfor beamforming. Using CPRI interfaces between the REC and the REexposing all 64 antennas for the REC would require approximately 54 CPRIinterfaces of 10 Gbps, since a CPRI interface carries about 480 MHz.Further, an interface using virtual antenna ports would require 4 MIMOstreams of 400 MHz, and would require about 4 CPRI interfaces of 10Gbps, since one 10 Gbps CPRI interface still carries data for about 480MHz. By also moving the modulation DL to the RE, the 4 MIMO streams of400 MHz would require 7 Gbps (assuming 256 QAM and 20 LTE 20 MHzcarriers), or one 10 Gbps CPRI interface. A higher bitrate of the CPRIinterface is required in the UL if the whole system bandwidth is used,as demodulation is still performed in the REC.

A general aspect of the inventive concepts disclosed herein is tomaximize the utilization of the REC-RE interface 700 between the REC 200a, 200 b and the RE 300 a, 300 b, both in the case where there is onlyone REC 200 a and when there are multiple RECs 200 a, 200 b sharing theREC-RE interface 700 (or segments of the REC-RE interface 700).

The embodiments disclosed herein thus relate to mechanisms forconfiguring transmission order of uplink data and prioritizedtransmission of uplink data. Unless otherwise stated the uplink datarefers to data transferred from the RE 300 a to the REC 200 on theREC-RE interface 700. Such uplink data could represent raw data asreceived on the radio interface 400 at the RE 300 a and forwarded by theRE 300 a to the REC 200 a. Alternatively, such uplink data couldrepresent refined data as determined by the RE 300 a, where the refineddata is based on raw data as received on the radio interface 400, andwhere the RE 300 a processes the raw data in order to determine therefined data. That is, the refined data is determined from the raw data.One non-limiting example of raw data is in-phase and quadrature (IQ)constellation points. One example of refined data is channel estimatevalues.

In order to obtain such mechanisms there is provided an REC 200, amethod performed by the REC 200, a computer program product comprisingcode, for example in the form of a computer program, that when run onprocessing circuitry of the REC 200, causes the REC 200 a to perform themethod. In order to obtain such mechanisms there is further provided anRE 300 a, 300 b, a method performed by the RE 300 a, 300 b, and acomputer program product comprising code, for example in the form of acomputer program, that when run on processing circuitry of the RE 300 a,300 b, causes the RE 300 a, 300 b to perform the method.

FIGS. 2 and 3 are flowcharts illustrating embodiments of methods forconfiguring transmission order of uplink data as performed by the REC200 a. FIGS. 4 and 5 are flowcharts illustrating embodiments of methodsfor prioritized transmission of uplink data as performed by the RE 300a, 300 b. The methods are advantageously provided as computer programs1320 a, 1320 b.

Reference is now made to FIG. 2 illustrating a method for configuringtransmission order of uplink data as performed by the REC 200 a of theaccess node 100 according to an embodiment. The REC 200 a has an REC-REinterface 700 to an RE 300 a, 300 b of the access node 100.

The REC 200 a configures the RE 300 a, 300 b in terms of prioritizedtransmission of uplink data. Particularly, the REC 200 a is configuredto perform step S106:

S106: The REC 200 a provides instructions to the RE 300 a, 300 b how toprioritize transmission order of uplink data. The uplink data isreceived by the RE 300 a, 300 b on a radio interface 400 and is to betransmitted from the RE 300 a, 300 b to the REC 200 a on the REC-REinterface 700. The REC 200 a thereby configures the transmission order(of the uplink data).

This enables the REC 200 to configure the RE 300 a, 300 b as needed. TheRE 300 a, 300 b does therefore not need to be pre-configured to use acertain prioritization mode. That is, the REC 200 a instructs the RE 300a, 300 b not only to prioritize the transmission order of the uplinkdata as such, but the REC 200 a instructs the RE 300 a, 300 b how theprioritization is to be performed, thereby enabling flexibleconfiguration of the RE 300 a, 300 b.

Embodiments relating to further details of configuring transmissionorder of uplink data as performed by the REC 200 a will now bedisclosed.

Reference is now made to FIG. 3 illustrating methods for configuringtransmission order of uplink data as performed by the REC 200 aaccording to further embodiments. It is assumed that step S106 isperformed as described above with reference to FIG. 2 and a thusrepeated description thereof is therefore omitted.

In some aspects the REC 200 a determines the prioritization (i.e., howthe transmission of the uplink data is to be prioritized) beforeproviding instructions to the RE 300 a, 300 b. Hence, according to anembodiment the REC 200 a is configured to perform step S102:

S102: The REC 200 a determines how the RE 300 a, 300 b is to prioritizethe transmission order of the uplink data.

The determination could be based on factors as will be given below.

In some aspects the prioritization is determined such that samples arereceived in order to be processed at baseband. Hence, according to anembodiment the transmission order is prioritized such that the uplinkdata is received by the REC 200 a in the order to be processed atbaseband. This allows the REC-RE interface 700 to be temporarilyover-utilized; the REC 200 a controls the prioritization of the samplessent from the RE in the UL to ensure that the samples are received inthe order they are going to be processed at baseband. This cuts over-alllatency.

In scenarios where a single REC 200 a is operatively connected to one ormore REs 300 a, 300 b the REC 200 a may directly configure this one ormore REs 300 a, 300 b. However, there might be scenarios where two ormore RECs 200 a, 200 b share one or more REs 300 a, 300 b.

That is, different RECs 200 a, 200 b might share the same RE 300 aand/or the REC-RE interface 700. An option would be to have a fixedallocation of the REC-RE interface 700 for each of the RECs 200 a, 200 bto act within. Another approach is to have the RECs 200 a, 200 bnegotiate for each subframe, or similar, on the best usage of the sharedresources (as defined by one or more REs 300 a, 300 b and/or the REC-REinterface 700). The RECs 200 a, 200 b might therefore coordinate andadjust the traffic through the one or more RE 300 a, 300 b to fit intothe available traffic capacity over the common REC-RE interface 700. Inmore detail, to handle scenarios with several RECs 200 a, 200 b, theremight be a coordinating function within the RECs 200 a, 200 bcommunicating with its neighboring RECs 200 a, 200 b, negotiating theuse of the available capacity of the REC-RE interface 700. In someaspects the REC 200 a thus negotiates with at least one other REC 200 bin conjunction with determining how to prioritize the transmission orderof the uplink data on the REC-RE interface 700. The negotiation couldcomprise exchanging information with this at least one other REC 200 b.Hence, according to an embodiment the REC 200 a is operatively connectedto a further REC 200 b that shares the REC-RE interface 700 to the RE300 a, 300 b with the REC 200 a. The REC 200 a could then be configuredto perform step S104:

S104: The REC 200 a negotiates with the further REC 200 b how toprioritize the transmission order of the uplink data to be transmittedfrom the RE 300 a, 300 b to the REC 200 a. The REC 200 a could furthernegotiate with the further REC 200 b how to prioritize transmissionorder of uplink data to be transmitted from the RE 300 a, 300 b to thefurther REC 200 b.

Such an exchange of planned usage between the RECs 200 a, 200 b couldavoid over-head (such as over-provisioning resulting from allocation ofadditional bandwidth) that otherwise would be needed to be reserved dueto unknown peaks in other REC usage. The RECs 200 a, 200 b sharing thesame RE 300 a, 300 b or sharing the REC-RE interface 700 can exchangeinformation on their proposed usage, and negotiate a fair split ofcapacity.

The sharing between the RECs 200 a, 200 b of the REC-RE interface 700can be done both by rate limiting on the transmitting side but also bysharing the REC-RE interface 700 in the time domain. A common prioritysetting among the scheduled transmissions (UL or DL) can be used to aidin determining when to transmit but also to support intermediate nodeson the link the preserve the relative priority. As an example, each REC200 a, 200 b could be configured to make a best case scheduling ofuplink transmission on the REC-RE interface 700 where it can assumehaving all resources on the REC-RE interface 700. The schedulingdecision is shared with other RECs 200 a, 200 b to coordinate with, anda joint prioritization can be made. Each REC 200 a, 200 b then yields tothe common prioritization. If the coordination is not done in time, oneor more RECs 200 a, 200 b could back off to a guaranteed portion of theREC-RE interface 700, e.g. an equal share.

Further, how to prioritize the transmission order is in some aspectsbased on requirements for maintaining a service for served terminaldevices 600. As an example, terminal devices 600 with strict decodinglatency requirements (due to such service) could be given acomparatively high priority. Hence, according to an embodiment, how toprioritize the transmission order is based on a criterion formaintaining a service associated with the uplink data.

In general terms, the data communication from the RE 300 a, 300 b to theREC 200 a is bursty. Most relevant data originates from the UL timeslots on the radio interface 400. The UL timeslots typically occupy ⅕ ofthe total time of the transfer of data from the REC 200 a to the RE 300a over the REC-RE interface 700; the remaining ⅘ of the total time isoccupied by DL timeslots. Significant cost savings can thus be made onthe REC-RE interface 700 if the UL related data is spread out over atime span longer than that of the UL timeslot duration.

In some aspects, UL user data is prioritized higher than UL measurementdata. As an example, UL measurement data (such as channel estimation orrefined channel estimations (delta information)) could be prioritizedlower than UL user data. In other aspects UL user data is prioritizedlower than UL measurement data. As an example, transmission ofdemodulation reference symbols could be given a comparatively highpriority. Hence, according to an embodiment the uplink data comprisesuser data and measurement data, and the RE 300 a, 300 b is instructed bythe RE 200 a to prioritize transmission of the user data higher thantransmission of the measurement data, or vice versa.

In some aspects, measurement data for non-stationary channels isprioritized higher than measurement data for stationary channels. Hence,according to an embodiment the uplink data comprises first measurementdata of a first radio propagation channel and second measurement data ofa second radio propagation channel, where the first radio propagationchannel is more non-stationary than the second radio propagationchannel. The RE 300 a, 300 b is then by the REC 200 a in step S106instructed to prioritize transmission of the first measurement datahigher than transmission of the second measurement data.

In some aspects, the prioritization is made per user, per beam, and/orper symbol. The symbols could be reference symbols. Hence, according toan embodiment the instructions pertain to at least one of prioritizationper terminal device 600 from which the uplink data is received by the RE300 a, 300 b, prioritization per beam 500 in which the uplink data isreceived by the RE 300 a, 300 b, and prioritization per symbol in theuplink data. In terms of priority per user (or terminal device 600),some users are more latency critical than others and symbols for thelatency critical users could be sent first. In terms of priority perbeam 500, different beams 500 of the same user could be given differentpriority. In contrast, commonly, excessively many beams 500 are orderedby the REC 200 a. Demodulation and decoding can start on a subset of thebeams 500 if latency prohibits waiting for all beams 500 to betransferred. In terms of priority per symbol, for any beam 500, thedemodulation reference symbols could be given priority over normal datasymbols, as the demodulation reference symbols in some respects areneeded earlier in the signal processing chain in the REC 200 a.

There could be different ways for the REC 200 a, to set the priorities(i.e., different ways for the REC 200 a to provide the instructions tothe RE 300 a, 300 b in step s106 how to prioritize transmission order ofuplink data). In some aspects the priorities are set by the REC 200 a inan UL control message (for a certain symbol or reception time slot).Hence, according to an embodiment the instructions in step S106 areprovided in an uplink control message.

In general terms, the REC-RE interface 700 carries user data symbolsassociated with terminal devices 600 and the bit rate will thus, amongother things, depend on the number of terminal devices 600 currentlybeing served by the access node 100 and on the amount of data that isreceived and transmitted to each served terminal devices 600. The CPRIinterface used today must be dimensioned according to the peak raterequirements independently of how it is actually used. This isillustrated in FIG. 6. FIG. 6 gives an illustrative example of thetraffic bit rate at the radio interface 400 of the RE 300 a as afunction of time. The REC-RE interface 700 could have a statisticaldimensioning, i.e. where the REC-RE interface 700 is not dimensionedaccording to the peak capacity. Hence, according to an embodiment, theREC-RE interface 700 has lower bit rate capacity for transmission of theuplink data than a peak bit rate at which the uplink data is received atthe RE 300 a, 300 b.

If a non-peak dimensioning is used it may happen that temporarily thereare many served terminal devices 600 requiring a temporary high capacityof the REC-RE interface 700. In such a case user data packets will bedropped on the REC-RE interface 700, resulting in retransmission overthe radio interface 400 to the terminal devices 600, thus wasting radioresources. This is also illustrated in FIG. 6. Therefore, according toan embodiment the instructions comprises a prioritization commandrelating to scheduling of the reception of the uplink data from terminaldevices 600, where the prioritization commands are to be applied at theRE 300 a, 300 b during reception of the uplink data. The RE 300 a, 300 bcan thereby be aware of the limitations of the REC-RE interface 700 andbe configured to adjust the amount of data that is scheduled over theradio interface 400 to fit into the available capacity of the REC-REinterface 700. That is, the scheduler of the radio interface 400 couldbe aware of the capacity of the REC-RE interface 700 and adjust theamount of data that is scheduled over the radio interface 400 to fitinto the available capacity of the REC-RE interface 700. That is,according to an embodiment the prioritization commands is based on thebit rate capacity of the REC-RE interface 700. The prioritizationcommand could be applicable to different types of data. Some examples ofsuch data are user data symbols, such as data on a physical downlinkshared channel (PDSCH) and data on a physical uplink shared channel(PUSCH), beam weights for the beamforming function in the RE 300 a, 300b and reference signals such as sounding reference signals (SRS) orreciprocity reference signals (RRS) for spatial observation of theterminal devices 600. Hence, according to an embodiment theprioritization command relates to reception of uplink data comprising atleast one of user data symbols, channel estimates, and referencesymbols.

According to an embodiment the prioritization command relates to atleast one of the number of terminal devices 600 to be scheduled, thenumber of layers to be scheduled for each terminal device 600 indownlink, the number of beams 500 to be scheduled for reception in theuplink, the amount of time/frequency resources to be available forreception of uplink data and transmission of downlink data, andadaptation of resolution in frequency of the time/frequency resources.Further aspects relating thereto will be disclosed below with referenceto the RE 300 a, 300 b.

There could be different ways for how often the instructions in steps106 are provided, or for how large amount of uplink data theinstructions are applicable. In an embodiment the instructions how theRE 300 a, 300 b is to prioritize received uplink data are provided tothe RE 300 a, 300 b per transmission time interval (TTI) of the uplinkdata. That is, according to this embodiment the instructions are thusvalid for one TTI. In this respect, the TTI is defined by the TTI of thetransmission and reception of the radio interface 400 of the RE 300 a,300 b.

In summary, by having the REC 200 a, 200 b being aware of the capacityof the REC-RE interface 700 and enabled to prioritize how uplink data isto be transmitted on the REC-RE interface 700, the usage of the REC-REinterface 700 can be optimized. An optimal use of the REC-RE interface700 could be made by, at each scheduling interval, prioritize how uplinkdata is to be transmitted on the REC-RE interface 700 according to thelimitations of the REC-RE interface 700, where the prioritizationpertains to adjustment of the resolution in time and/or frequency forweight information, number of terminal devices 600, beams 600 andlayers. Further, in scenarios with two or more RECs 200 a, 200 b, eachREC 200 a, 200 b could be configured to coordinate the usage of theREC-RE interface 700 with its neighbors in order to optimize the usageof the REC-RE interface 700. An optimal use of the REC-RE interface 700could then be made by, at each scheduling interval, coordinate thescheduling among RECs 200 a, 200 b at each scheduling interval so as toprioritize how uplink data is to be transmitted on the REC-RE interface700 according to the limitations of the REC-RE interface 700, where theprioritization pertains to adjustment of the resolution in time and/orfrequency for weight information, number of terminal devices 600, beams600 and layers.

Reference is now made to FIG. 4 illustrating a method for prioritizedtransmission of uplink data as performed by the RE 300 a of the accessnode 100 according to an embodiment. The RE 300 a has an REC-REinterface 700 to the REC 200 a of the access node 100.

As disclosed above, the REC 200 a in step S106 provides instructions tothe RE 300 a how to prioritize the transmission order of uplink data onthe REC-RE interface 700. It is assumed that these instructions arereceived by the RE 300 a. Hence, the RE 300 a is configured to performstep S202:

S202: The RE 300 a receives instructions from the REC 200 a how toprioritize transmission order of uplink data. The uplink data isreceived by the RE 300 a, 300 b on a radio interface 400 and is to betransmitted from the RE 300 a, 300 b to the REC 200 a on the REC-REinterface 700.

The RE 300 a then acts accordingly and is hence configured to performstep S206:

S206: The RE 300 a transmits the uplink data on the REC-RE interface 700according to the instructions, resulting in prioritized transmission ofthe uplink data. The uplink data is thus transmitted on the interface inan order as given by the instructions provided by the REC 200 a.

Embodiments relating to further details of prioritized transmission ofuplink data as performed by the RE 300 a, 300 b will now be disclosed.

As disclosed above, according to an embodiment the prioritizationcommand relates to at least one of the number of terminal devices 600 tobe scheduled, the number of layers to be scheduled for each terminaldevice 600 in downlink, the number of beams 500 to be scheduled forreception in the uplink, the amount of time/frequency resources to beavailable for reception of uplink data and transmission of downlinkdata, and adaptation of resolution in frequency of the time/frequencyresources. In terms of the number of scheduled terminal devices 600, incase of comparatively high utilization of the REC-RE interface 700, lessterminal devices 600 can be scheduled. In terms of the number of layersthat are scheduled for each terminal device 600 in DL, in case ofcomparatively high utilization of the REC-RE interface 700 less layerscan be scheduled. In terms of the number of beams 500 that are scheduledfor reception in UL, in case of comparatively high utilization of theREC-RE interface 700 less beams 500 can be scheduled. In terms of theamount of time/frequency resources used for transmission and reception(such as the number of subcarriers used for each TTI), in case ofcomparatively high utilization of the REC-RE interface 700 lesstime/frequency resources (subcarriers) can be used. In terms ofadaptation of resolution in frequency of the time/frequency resources,to reduce the bit rate used for uplink transmission on the REC-REinterface 700, beam weights and spatial information can be expressed fora larger number of sub-carriers i.e., for a larger bandwidth, in case ofcomparatively high utilization of the REC-RE interface 700.

Reference is now made to FIG. 5 illustrating methods for prioritizedtransmission of uplink data as performed by the RE 300 a, 300 baccording to further embodiments. It is assumed that steps S202, S206are performed as described above with reference to FIG. 4 and a thusrepeated description thereof is therefore omitted.

As disclosed above, in some aspects the instructions in step S106 areprovided in an uplink control message, as is sent from the REC 200 a tothe RE 300 a. Hence, according to an embodiment the instructions are instep S206 received in an uplink control message.

As disclosed above, in some aspects the instructions comprise aprioritization command relating to scheduling of the reception of theuplink data from terminal devices 600. The prioritization commands areto be applied at the RE 300 a, 300 b during reception of the uplinkdata. Hence, according to an embodiment the RE 300 a is configured toperform step S204:

S204: The RE 300 a schedules the reception of the uplink data from theterminal devices 600 in accordance with the prioritization command.

As disclosed above, in some aspects the instructions how the RE 300 a,300 b is to prioritize received uplink data are provided to the RE 300a, 300 b per TTI of the uplink data.

Further aspects and embodiments applicable to both the methods performedby the REC 200 a and the RE 300 a disclosed above will now be provided.

In a time division duplex (TDD) system, the UL samples are generatedduring a short time, namely during UL radio subframes. As disclosedabove, the herein disclosed embodiments enable the REC-RE interface 700to be dimensioned lower than the peak bit rate generated at thereceiving radio interface. This can be accomplished by spreading out thetransmission of uplink data on the REC-RE interface 700 also over theduration of the DL subframes. Further, the uplink data could betransmitted in an order which minimize the impact of the REC-REinterface 700 given that parallelized signal processing is used in theREC 200 a.

Different ways to spread out the transmission of uplink data on theREC-RE interface 700 will now be disclosed.

According to a first example the transmission of uplink data on theREC-RE interface 700 is spread out by the RE 200 a determining thepriority of the users (terminal devices 600) and the measurementscarried out during the UL subframe. This gives a first order. Thepriority of the users could depend on the service, e.g. end-to-endrequirements. The priority of the users could depend on whether the useris going to be scheduled DL shortly after the prioritization determiningis performed or not. Users not scheduled DL soon after can be givenlower priority as result anyway would be on hold. The priority of theusers could depend on whether the user is affecting another higherpriority user or not, e.g. if interference cancellation is required. Thepriority of the users could depend on whether the uplink data of theuser is requested by another access node.

According to a second example the transmission of uplink data on theREC-RE interface 700 is spread out by the RE 200 a determining thepriority of each set of samples for each user (terminal device 600).Demodulation reference symbols could be given higher priority than datasamples to allow for the demodulation to start early. Processing of datain the RE 300 a needed for processing in the REC 200 a could beprioritized over processing of data not needed for processing in the REC200 a such that data needed for processing in the REC 200 a could betransferred to the REC 200 a over the REC-RE interface 700 before datanot needed for processing in the REC 200 a is transferred to the REC 200a over the REC-RE interface 700. Different beams 500 could be givendifferent priority; the REC 200 could determine a minimal number ofbeams for the decoding and set higher priority of these beams.Measurement samples not needed for instant decoding, but rather forfuture link adaptation and beam shaping could be given low priority. Bysending the demodulation symbols first for multiple users, the signalprocessing in the REC 200 a can start calculating channel estimates inparallel. Typically, signal processing consists of a large set ofprocessing units which can be subdivided to in parallel calculatechannel estimates for the users.

FIGS. 7 and 8 show an example of the prioritization of uplink data. FIG.7 illustrates allocation of resources in a time/frequency grid. Theresources are provided in terms of physical resource blocks (PRBs;numbered “1” to “13” in FIG. 7) and subframes (denoted “Subframe 1” and“Subframe 2” in FIG. 7) where in each subframe the resources areallocated to a beam 500 (denoted “Beam 1”, “Beam 2”, “Beam 3”, and “Beam4” in FIG. 7).

Further, in the illustrative example of FIG. 7, uplink data for threeusers (“User A”, “User B”, and “User C”) is allocated to the resources.“User A” uses two of the beams (“Beam 1” and “Beam 2”) and is assumed tohave highest priority. “User B” uses all of the beams and a differentnumber of PRBs in the two subframes and is assumed to have middlepriority. “User C” uses all of the beams and is assumed to have lowestpriority.

FIG. 8 illustrates the resulting order “a”-“k” in which the dataallocated to the users in FIG. 7 is to be transmitted on the REC-REinterface 700, where the data in “a” to “k” is given according to Table1:

TABLE 1 Transmission order of uplink data according to FIG. 8 aReference symbols for “User A” b Reference symbols for “User B” c Datasymbols for “User A” d Data symbols for “User B” e First part ofreference and data symbols for “User C” from “Subframe 1”. Not allreference and data symbols is transferred as “User C” has lowestpriority and must accept a longer latency f Reference symbols for “UserA” g Reference symbols for “User B” h Data symbols for “User A” i Datasymbols for “User B” j Second part of reference and data symbols for“User C” from “Subframe 1”and reference and data symbols for “User C”from “Subframe 2” k Measurement data for all user, such as additionalsamples, channel estimates, SRS measurements, etc.

FIG. 9 schematically illustrates, in terms of a number of functionalunits, the components of an REC 200 a according to an embodiment.Processing circuitry 210 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1310 a (as in FIG. 13), e.g. in the form of a storage medium 230. Theprocessing circuitry 210 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 210 is configured to cause theREC 200 a to perform a set of operations, or steps, S102-S106, asdisclosed above. For example, the storage medium 230 may store the setof operations, and the processing circuitry 210 may be configured toretrieve the set of operations from the storage medium 230 to cause theREC 200 a to perform the set of operations. The set of operations may beprovided as a set of executable instructions. Thus the processingcircuitry 210 is thereby arranged to execute methods as hereindisclosed.

The storage medium 230 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The REC 200 a further comprises a communications interface 220 forcommunications with other entities of the access node 100, such asanother REC 200 b and one or more REs 300 a, 300 b. As such thecommunications interface 220 may comprise one or more transmitters andreceivers, comprising analogue and digital components. Thecommunications interface 220 is operatively connected to the REC-REinterface 700.

The processing circuitry 210 controls the general operation of the REC200 a e.g. by sending data and control signals to the communicationsinterface 220 and the storage medium 230, by receiving data and reportsfrom the communications interface 220, and by retrieving data andinstructions from the storage medium 230. Other components, as well asthe related functionality, of the REC 200 a are omitted in order not toobscure the concepts presented herein.

FIG. 10 schematically illustrates, in terms of a number of functionalmodules, the components of an REC 200 a according to an embodiment. TheREC 200 a of FIG. 10 comprises a provide module 210C configured toperform step S106. The REC 200 a of FIG. 10 may further comprise anumber of optional functional modules, such as any of a determine module210 a configured to perform step S102, and a negotiate module 210 bconfigured to perform step S104. In general terms, each functionalmodule 210 a-210 c may be implemented in hardware or in software.Preferably, one or more or all functional modules 210 a-210 c may beimplemented by the processing circuitry 210, possibly in cooperationwith the communications interface 220 and/or the storage medium 230. Theprocessing circuitry 210 may thus be arranged to from the storage medium230 fetch instructions as provided by a functional module 210 a-210 cand to execute these instructions, thereby performing any steps of theREC 200 a as disclosed herein.

FIG. 11 schematically illustrates, in terms of a number of functionalunits, the components of an RE 300 a, 300 b according to an embodiment.Processing circuitry 310 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1310 b (as in FIG. 13), e.g. in the form of a storage medium 330. Theprocessing circuitry 310 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 310 is configured to cause the RE300 a, 300 b to perform a set of operations, or steps, S202-S206, asdisclosed above. For example, the storage medium 330 may store the setof operations, and the processing circuitry 310 may be configured toretrieve the set of operations from the storage medium 330 to cause theRE 300 a, 300 b to perform the set of operations. The set of operationsmay be provided as a set of executable instructions. Thus the processingcircuitry 310 is thereby arranged to execute methods as hereindisclosed.

The storage medium 330 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The RE 300 a, 300 b further comprises a communications interface 320 forcommunications other entities of the access node 100, such as one ormore RECs 200 a, 200 b. As such the communications interface 320 maycomprise one or more transmitters and receivers, comprising analogue anddigital components. The communications interface 320 is operativelyconnected to the REC-RE interface 700.

The processing circuitry 310 controls the general operation of the RE300 a, 300 b e.g. by sending data and control signals to thecommunications interface 320 and the storage medium 330, by receivingdata and reports from the communications interface 320, and byretrieving data and instructions from the storage medium 330. Othercomponents, as well as the related functionality, of the RE 300 a, 300 bare omitted in order not to obscure the concepts presented herein.

FIG. 12 schematically illustrates, in terms of a number of functionalmodules, the components of an RE 300 a, 300 b according to anembodiment. The RE 300 a, 300 b of FIG. 12 comprises a number offunctional modules; a receive module 310 a configured to perform stepS210 and a transmit module 310 c configured to perform step S206. The RE300 a, 300 b of FIG. 12 may further comprise a number of optionalfunctional modules, such as a schedule module 310 b configured toperform step S204. In general terms, each functional module 310 a-310 cmay be implemented in hardware or in software. Preferably, one or moreor all functional modules 310 a-310 c may be implemented by theprocessing circuitry 310, possibly in cooperation with thecommunications interface 320 and/or the storage medium 330. Theprocessing circuitry 310 may thus be arranged to from the storage medium330 fetch instructions as provided by a functional module 310 a-310 cand to execute these instructions, thereby performing any steps of theRE 300 a, 300 b as disclosed herein.

The RE and REC may be provided as standalone devices or as a part of atleast one further device. For example, as disclosed above the RE and RECmay be provided in an access node. Alternatively, functionality of theRE and the REC may be distributed between at least two devices, ornodes.

Thus, a first portion of the instructions performed by the RE or REC maybe executed in a first device, and a second portion of the of theinstructions performed by the RE or REC may be executed in a seconddevice; the herein disclosed embodiments are not limited to anyparticular number of devices on which the instructions performed by theRE or REC may be executed. Hence, the methods according to the hereindisclosed embodiments are suitable to be performed by an RE or RECresiding in a cloud computational environment. Therefore, although asingle processing circuitry 210, 310 is illustrated in FIGS. 9 and 11the processing circuitry 210, 310 may be distributed among a pluralityof devices, or nodes. The same applies to the functional modules 210a-210 c, 310 a-310 c of FIGS. 10 and 12 and the computer programs 1320a, 1320 b of FIG. 13 (see below).

FIG. 13 shows one example of a computer program product 1310 a, 1310 bcomprising computer readable means 1330. On this computer readable means1330, a computer program 1320 a can be stored, which computer program1320 a can cause the processing circuitry 210 and thereto operativelycoupled entities and devices, such as the communications interface 220and the storage medium 230, to execute methods according to embodimentsdescribed herein. The computer program 1320 a and/or computer programproduct 1310 a may thus provide means for performing any steps of theREC 200 a as herein disclosed. On this computer readable means 1330, acomputer program 1320 b can be stored, which computer program 1320 b cancause the processing circuitry 310 and thereto operatively coupledentities and devices, such as the communications interface 320 and thestorage medium 330, to execute methods according to embodimentsdescribed herein. The computer program 1320 b and/or computer programproduct 1310 b may thus provide means for performing any steps of the RE300 a, 300 b as herein disclosed.

In the example of FIG. 13, the computer program product 1310 a, 1310 bis illustrated as an optical disc, such as a CD (compact disc) or a DVD(digital versatile disc) or a Blu-Ray disc. The computer program product1310 a, 1310 b could also be embodied as a memory, such as a randomaccess memory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM), or an electrically erasable programmableread-only memory (EEPROM) and more particularly as a non-volatilestorage medium of a device in an external memory such as a USB(Universal Serial Bus) memory or a Flash memory, such as a compact Flashmemory. Thus, while the computer program 1320 a, 1320 b is hereschematically shown as a track on the depicted optical disk, thecomputer program 1320 a, 1320 b can be stored in any way which issuitable for the computer program product 1310 a, 1310 b.

The inventive concept has mainly been described above with reference toa few embodiments. However, as is readily appreciated by a personskilled in the art, other embodiments than the ones disclosed above areequally possible within the scope of the inventive concept, as definedby the appended patent claims.

The invention claimed is:
 1. A method for configuring transmission orderof uplink data, the method performed by a radio equipment controller(“REC”) of an access node, the REC having a REC-radio equipment (“RE”)interface that communicatively couples the REC with a RE of the accessnode, the method comprising: scheduling uplink transmission on a radiointerface between the access node and one or more terminal devices; andproviding transmission order instructions to the RE that indicate ascheduling prioritization for transmission by the RE of uplink databetween the RE and the REC over the REC-RE interface, the uplink databeing received by the RE on the radio interface.
 2. The method of claim1, wherein the transmission order instructions comprise instructionscorresponding to prioritization per terminal device and/or beam fromwhich the uplink data is received by the RE.
 3. The method of claim 1,wherein the transmission order instructions comprise instructions tocause reference symbols in the uplink data to be prioritized over othertypes of uplink data.
 4. The method of claim 1, wherein the transmissionorder instructions comprise instructions to prioritize transmission ofuser data relative to transmission of measurement data.
 5. The method ofclaim 1, wherein the transmission order instructions compriseinstructions to cause the RE to prioritize transmission of a firstmeasurement data of a first radio propagation channel higher thantransmission of a second measurement data of a second radio propagationchannel.
 6. The method of claim 1, wherein the transmission orderinstructions are based on a bit rate capacity of an interface betweenthe REC and the RE.
 7. The method of claim 1, wherein providing thetransmission order instructions comprises providing the transmissionorder instructions to the RE per transmission time interval of theuplink data.
 8. The method of claim 1, wherein providing thetransmission order instructions comprises transmitting an uplink controlmessage that includes the transmission order instructions.
 9. The methodof claim 1, wherein the REC is a first REC, the method furthercomprising: determining a prioritization corresponding to uplink datathat is transmitted by the RE; exchanging, with a second REC,information regarding the prioritization; and receiving, from the RE, atransmission of the uplink data according to the provided transmissionorder instructions, wherein providing transmission order instructionscomprises providing, based on the exchanged information, thetransmission order instructions to the RE.
 10. The method of claim 9,wherein receiving the transmission of the uplink data comprisesreceiving the uplink data from the RE in an order that the uplink datais to be baseband processed.
 11. The method of claim 9, whereindetermining the prioritization comprises determining the transmissionorder instructions based on a criterion for maintaining a serviceassociated with the uplink data.
 12. A non-transitory computer-readablemedium comprising computer-readable instructions which, when executed bya processor of a radio equipment controller (“REC”) of an access node,causes the REC to perform operations, wherein the REC has a REC-radioequipment (“RE”) interface that communicatively couples the REC with aRE of the access node, the operations comprising: scheduling uplinktransmission from one or more terminal devices on a radio interface; andproviding transmission order instructions to the RE that indicate ascheduling prioritization for transmission by the RE of uplink databetween the RE and the REC over the REC-RE interface, the uplink databeing received by the RE on the radio interface.
 13. The non-transitorycomputer-readable medium of claim 12, wherein the transmission orderinstructions comprise instructions corresponding to prioritization perterminal device and/or beam from which the uplink data is received bythe RE.
 14. The non-transitory computer-readable medium of claim 12,wherein the transmission order instructions comprise instructions tocause reference symbols in the uplink data to be prioritized over othertypes of uplink data.
 15. The non-transitory computer-readable medium ofclaim 12, wherein the transmission order instructions compriseinstructions to prioritize transmission of user data relative totransmission of measurement data.
 16. The non-transitorycomputer-readable medium of claim 12, wherein the transmission orderinstructions comprise instructions to cause the RE to prioritizetransmission of a first measurement data of a first radio propagationchannel higher than transmission of a second measurement data of asecond radio propagation channel.
 17. The non-transitorycomputer-readable medium of claim 12, wherein the transmission orderinstructions are based on a bit rate capacity of an interface betweenthe REC and the RE.
 18. The non-transitory computer-readable medium ofclaim 12, wherein providing the transmission order instructionscomprises providing the transmission order instructions the RE pertransmission time interval of the uplink data.
 19. The non-transitorycomputer-readable medium of claim 12, wherein providing the transmissionorder instructions comprises transmitting an uplink control message thatincludes the transmission order instructions.
 20. The non-transitorycomputer-readable medium of claim 12, wherein the REC is a first REC,the operations further comprising: determining a prioritizationcorresponding to uplink data that is transmitted by the RE; exchanging,with a second REC, information regarding the prioritization; andreceiving, from the RE, a transmission of the uplink data according tothe provided transmission order instructions, wherein providingtransmission order instructions comprises providing, based on theexchanged information, the transmission order instructions to the RE.21. The non-transitory computer-readable medium of claim 20, whereinreceiving the transmission of the uplink data comprises receiving theuplink data from the RE in an order that the uplink data is to bebaseband processed.
 22. The non-transitory computer-readable medium ofclaim 20, wherein determining the prioritization comprises determiningthe transmission order instructions based on a criterion for maintaininga service associated with the uplink data.
 23. A radio equipmentcontroller (“REC”) of an access node, the REC having a REC-radioequipment (“RE”) interface that communicatively couples the REC with aRE of the access node, the REC comprising: processing circuitry; andmemory coupled to the processing circuitry and having instructionsstored therein that are executable by the processing circuitry to causethe REC to perform operations comprising: scheduling uplink transmissionfrom one or more terminal devices on radio interface; and providingtransmission order instructions to the RE that indicate a schedulingprioritization for transmission by the RE of uplink data between the REand the REC over the REC-RE interface, the uplink data being received bythe RE on the radio interface.
 24. The REC of claim 23, wherein thetransmission order instructions are based on a bit rate capacity of theinterface to the RE.
 25. The REC of claim 23, wherein providing thetransmission order instructions comprises providing the transmissionorder instructions to the RE per transmission time interval of theuplink data.
 26. The REC of claim 23, wherein the transmission orderinstructions comprise instruction to cause reference symbols in theuplink data to be prioritized over other types of uplink data.
 27. TheREC of claim 23, wherein the transmission order instructions compriseinstructions to prioritize transmission of user data relative totransmission of measurement data.
 28. The REC of claim 23, wherein thetransmission order instructions comprise instructions to cause the RE toprioritize transmission of a first measurement data of a first radiopropagation channel higher than transmission of a second measurementdata of a second radio propagation channel.
 29. The REC of claim 23,wherein providing the transmission order instructions comprisestransmitting an uplink control message that includes the transmissionorder instructions.
 30. The REC of claim 23, wherein the REC is a firstREC, the operations further comprising: determining a prioritizationcorresponding to uplink data that is transmitted by the RE; exchanging,with a second REC, information regarding the prioritization; andreceiving, from the RE, a transmission of the uplink data according tothe provided transmission order instructions, wherein providingtransmission order instructions comprises providing, based on theexchanged information, the transmission order instructions to the RE.31. The REC of claim 30, wherein receiving the transmission of theuplink data comprises receiving the uplink data from the RE in an orderthat the uplink data is to be baseband processed.
 32. The REC of claim30, wherein determining the prioritization comprises determining thetransmission order instructions based on a criterion for maintaining aservice associated with the uplink data.